Affected CI (Configuration Item) iCube enables you to create ad hoc reports that help you to understand the number of CIs affected due to specific incidents, or problems or the number of incidents or problems affecting a specific CI.
Attribute Name | Description |
---|---|
Affected CI | Configuration Item that is affected by a Task |
Affected CI Associated On | Date on which the CI is added to the list of affected CIs related to a Task |
Primary Affected CI Flag |
Flag indicating if this is the primary CI of the affecting Task. A value of Y or N indicates if this is the primary CI or not. |
Task Affecting CI | Task that is affecting the CI. It can be any task like Incident , Change Request, Problem, or Outage. |
Task Number (Affecting CI) | Unique identifier of the Task that is affecting the CI |
Task Opened On (Affecting CI) | Date when the affecting Task was opened |
Task Type (Affecting CI) | Type of the affecting Task such as Incident, Problem, Change Request, or Outage |
Metric Name | Description | Formula | Expected Values |
---|---|---|---|
Affected CI Count | Count of distinct affected Configuration Items against the Tasks that are selected in the context for analysis. | Max([Affected CI Count]) {~} | 0 or >0 |
Affecting Task Count | Count of distinct affecting Tasks against the Configuration Items that are in the context for analysis. | Max([Affecting Task Count]) {~} | 0 or >0 |
© 2022 Digital.ai Inc. All rights reserved.